Intervention History
hybridThe node memory and audit trail.
Purpose
History stores what happened, when it happened, what changed, and what evidence supports it. It is the memory that lets one node teach another.
When to Use
- After every completed task
- Before repeating a previous intervention
- When exporting playbooks
- When proving impact to a peer node
Best First Action
Filter to completed tasks and review the pillar shift chart for the last successful intervention.
Content
Purpose
History stores what happened, when it happened, what changed, and what evidence supports it. It is the memory that lets one node teach another.
When to Use
- After every completed task
- Before repeating a previous intervention
- When exporting playbooks
- When proving impact to a peer node
Best First Action
Filter to completed tasks and review the pillar shift chart for the last successful intervention.
Best Practices
- Attach verification photos or CIDs when possible.
- Use notes to preserve local knowledge.
- Do not edit history; append corrections instead.
- Export history with CRK bundles for peer learning.
Common Mistakes
- Treating history as clutter instead of institutional memory.
- Failing to attach evidence.
- Deleting logs that explain why a design changed.
Next Steps
- Open CRK to export bundles.
- Open Network to share mission results.
- Promote proven interventions into future playbooks.
Best Practices
- Attach verification photos or CIDs when possible.
- Use notes to preserve local knowledge.
- Do not edit history; append corrections instead.
- Export history with CRK bundles for peer learning.
Common Mistakes
- Treating history as clutter instead of institutional memory.
- Failing to attach evidence.
- Deleting logs that explain why a design changed.
Next Steps
- Open CRK to export bundles.
- Open Network to share mission results.
- Promote proven interventions into future playbooks.